Power capping feedback normalization

ABSTRACT

A power capping system ( 10 ) and method ( 200 ) are provided. In one embodiment, a power capping system ( 10 ) includes a power controller ( 16 ) configured to calculate an error between a predefined maximum desired power and a power feedback signal associated with actual power consumption of a server ( 12 ) and to provide a power capping signal that substantially limits the power consumption of the server ( 12 ) based on a predetermined gain constant and the error. The system also includes a management interface ( 18 ) configured to generate a normalization factor based on the power feedback signal. The normalization factor can be implemented to normalize the error.

BACKGROUND

Power capping is a process in which a power capping signal is providedto a server to substantially limit the power consumption of the serverby throttling one or more processors and/or memory components. Powercapping fast enough to protect circuit breakers can require afast-acting power capping controller that utilizes closed-loop feedbackcontrol. However, adjusting a gain of the closed-loop feedback controlcan be complicated. As an example, a gain that is too low can result inthe controller's response being too slow, and a gain that is too highcan result in oscillation of the power capping that may not settle.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example embodiment of a power capping system.

FIG. 2 illustrates another example embodiment of a power capping system.

FIG. 3 illustrates an example embodiment of a data conversion system ina power capping system.

FIG. 4 illustrates yet another example embodiment of a power cappingsystem.

FIG. 5 illustrates an example embodiment of a method for normalizingerror in a power capping system associated with a server.

DETAILED DESCRIPTION

FIG. 1 illustrates an example of a power capping system 10. The powercapping system 10 can be implemented to substantially limit a powerconsumption associated with a server 12 that includes one or moreprocessors 14. As an example, the server 12 could also include one ormore memory devices (not shown), as well, such as one or more dualin-line memory modules (DIMMs).

The power capping system 10 includes a power controller 16 and amanagement interface 18. The power controller 16 can implement a controlloop to generate a power capping signal POW_CAP that is provided to theserver 12 to substantially limit the power consumption of the server 12.Specifically, the power controller 16 can set a control percentage ofthe power capping signal POW_CAP that can set the processors 14 in theserver 12 to a low-processing state, such as by lowering a power voltageand/or slowing down a processor clock signal. As an example, the powercapping signal POW_CAP can be a PROCHOT# signal, and the power cappingcontrol percentage can be a duty-cycle associated with the power cappingsignal POW_CAP. As another example, the power capping signal POW_CAPcould initiate a sequence that writes to specific control registersinside the processors 14 that lower the power consumption of theprocessors 14, such as by lowering power voltage and/or speed.

To generate the power capping signal POW_CAP, the power controller 16monitors an actual power consumption of the server 12 via a powerfeedback signal POW_FB that is generated by a power meter 20. The powercontroller 16 includes an error calculator 22 that is configured tocalculate an amount of error between the power feedback signal POW_FBand a predefined maximum desired power that is specified by a signalCAP. As an example, the signal CAP can define a user specified maximumdesired operating power associated with the server 12. The error that iscalculated by the error calculator 22 can be multiplied by apredetermined gain constant K that is provided to the power controller16, and the result can be integrated and modulated to set the controlpercentage of the power capping signal POW_CAP. As an example, themodulation can be pulse-width modulation to set a duty-cycle of thepower capping signal POW_CAP.

The management interface 18 can be an embedded server interface, such asan Integrated Lights Out (iLO) management interface. The managementinterface 18 includes a normalization calculator 24 that is configuredto provide a normalization factor N to the power controller 16 tonormalize the error that is calculated by the error calculator 22. As anexample, the predetermined gain constant K can be generated for aplurality of different servers, including the server 12, that all havedifferent functionality, and thus power consumption demands. Thus, theerror that is calculated by the error calculator 22 can be normalized toaccommodate the specific power consumption demands of the server 12 suchthat the predetermined gain constant K can remain common to the set ofall servers.

The management interface 18 can be configured to initiate a calibrationprocedure that is signaled to the power controller 16 and the server 12via a signal CAL, such as subsequent to manufacture of the server 12and/or at start-up of the server 12. During the calibration procedure,the management interface 18 can command the server 12 to run aprocessing intense program, such that the power consumption of theserver 12 is substantially maximized independently of the power cappingsignal POW_CAP. As an example, the processing intense program caninclude a series of dummy floating-point calculations and/or otherprocessing operations that substantially maximize processing capabilityof the server 12. The management interface 18 can then adjust thecontrol percentage of the power capping signal POW_CAP between a firstvalue and a second value. As an example, the first value can beapproximately 0% (i.e., full power) and the second value can beapproximately 100% (i.e., full power capping). The management interface18 can thus measure the actual power consumption of the server 12 ateach of the separate control percentage values of the power cappingsignal POW_CAP and calculate a difference to generate the normalizationfactor N. Accordingly, the power controller 16 can set the controlpercentage of the power capping signal POW_CAP based on the errorcalculated by the error calculator 22 and a factor associated with thenormalization factor N and the predetermined gain constant K.

It is to be understood that the power capping system 10 is not intendedto be limited to the example of FIG. 1. As an example, the featuresassociated with the power controller 16 and/or the management interface18 can be implemented as software or a combination of hardware andsoftware. In addition, at least one of the power controller 16 and themanagement interface 18 can be configured in or in a portion of anintegrated circuit (IC). As another example, the predetermined gainconstant K can be provided to the management interface 18 instead of thepower controller 16. As an example, the power controller 16 may beconfigured with substantial limited processing capability, such as toprevent certain arithmetic operations (e.g., division). Thus, themanagement interface 18 could be configured to provide the normalizationfactor N as a factor that also includes the predetermined gain constantK, as described in greater detail in the example of FIG. 3 below. Thus,the power capping system 10 can be configured in a variety of ways.

FIG. 2 illustrates another example embodiment of a power capping system50. As an example, the power capping system 50 can represent a portionof the power capping system 10 in the example of FIG. 1. The powercapping system 50 includes a power controller 52 and a managementinterface 54.

Similar to as described above in the example of FIG. 1, the powercontroller 52 implements a control loop to generate a power cappingsignal POW_CAP that is provided to a server (not shown) to substantiallylimit the power consumption of the server. The power controller 52includes a summation component 56 that is configured to subtract asignal CAP from a power feedback signal POW_FB that corresponds to theactual power consumption of the server. As an example, the signal CAPcan define a user specified maximum desired operating power associatedwith the server. The summation component 56 thus outputs an error factorERR corresponding to an error associated with the power feedback signalPOW_FB, and thus the actual power consumption of the server, relative tothe signal CAP.

The error factor ERR is provided to an arithmetic unit 58 that isconfigured to multiply the error represented by the error factor ERR bya factor that is associated with a predetermined gain constant K and anormalization factor N. Specifically, the arithmetic unit 58 isconfigured to multiply the error factor ERR by the predetermined gainconstant K and to divide the result by the normalization factor N. As anexample, the predetermined gain constant K can be a gain constant thatis calculated for a plurality of servers, such that the predeterminedgain constant K can be common to each of the plurality of servers. Thenormalization factor N can be generated by the management interface 54,as described in greater detail below. Thus, by dividing the product ofthe error factor ERR and the predetermined gain constant K by thenormalization factor N, the error factor ERR is normalized to implementpower capping in a manner that is specific to the server. The normalizederror is output from the arithmetic component 58 as a normalized errorfactor N_ERR.

The normalized error factor N_ERR is provided to an integrator 60 thatis configured to integrate the normalized error with respect to previousvalues of error. The integrated error INT is output from the integrator60 to a pulse-width modulator 62 that is configured to set a duty-cycleof the power capping signal POW_CAP based on the integrated error INT.Specifically, the pulse-width modulator 62 pulse-width modulates thepower capping signal POW_CAP to set a pulse-width that is inverselyproportional to the power consumption of the server.

The management interface 54 can be configured, for example, as anembedded server interface. The management interface 54 includes acalibration controller 64 that provides a calibration signal CAL toinitiate a calibration procedure. As an example, the calibration signalCAL in the example of FIG. 2 can correspond to one or more signalsand/or software code sequences that are activated to initiate thecalibration procedure. The calibration signal CAL can be provided to theserver to initiate a processing intense program, such that the powerconsumption of the server is substantially maximized independently ofthe power capping signal POW_CAP. As an example, the processing intenseprogram can include a series of dummy floating-point calculations and/orother processing operations that substantially maximize processingcapability of the server. The processing intense program can be storedon the server, such that the calibration signal CAL initiates executionof the processing intense program, or it can be stored on the managementinterface 54, such that it can be downloaded to the server via thecalibration signal CAL.

The calibration signal CAL can also be provided to the pulse-widthmodulator 62 to adjust the duty-cycle of the power capping signalPOW_CAP during the calibration procedure. As an example, prior to orsubsequent to initiating the processing intense program, the calibrationsignal CAL can command the pulse-width modulator 62 to vary theduty-cycle of the power capping signal POW_CAP between approximately 0%(i.e., fully off) and approximately 100% (i.e., fully on). Themanagement interface 54 also includes a power monitor 66 that isconfigured to monitor the magnitude of the power feedback signal POW_FB,and thus the actual power consumption of the server. The power monitor66 can thus save the values of the power feedback signal POW_FBcorresponding to when the power capping signal POW_CAP has a 0%duty-cycle, indicated by a 0% CAPPING component 68, and when the powercapping signal POW_CAP has a 100% duty-cycle, indicated by a 100%CAPPING component 70. As an example, the calibration controller 64 canprovide a storage signal STORE to command the power monitor 66 to storethe values at the appropriate times. For example, the storing of thevalues of the power feedback signal POW_FB can be delayed for apredetermined amount of time after the duty-cycle of the power cappingsignal POW_CAP is set to 0% and 100%, respectively, based on the storagecommand provided by the storage signal STORE.

The management interface 54 also includes a summation component 72 thatis configured to subtract the value of the power feedback signal POW_FBat 100% duty-cycle of the power capping signal POW_CAP from the value ofthe power feedback signal POW_FB at 0% duty-cycle of the power cappingsignal POW_CAP. The result is the normalization factor N correspondingto the difference between a minimum power consumption and a maximumpower consumption of the server. Thus, the normalization factor N isimplemented to normalize the error that is calculated in the powercontroller 52, such that the predetermined gain constant K can be commonto a plurality of servers, such as a plurality of servers that aremanufactured/tested/validated together. As a result, each of theindividual servers do not have to be individually tuned to calculaterespective individual gain constants.

It is to be understood that the power capping system 50 is not intendedto be limited to the example of FIG. 2. As an example, the featuresassociated with the power controller 52 and/or the management interface54 can be implemented as software or a combination of hardware andsoftware. In addition, at least one of the power controller 52 and themanagement interface 54 can be configured in or in a portion of anintegrated circuit (IC). As yet another example, the calculation of thenormalization factor N can occur in real-time instead of during acalibration procedure. For example, the power monitor 66 may monitor thepower feedback signal POW_FB at various values of the duty-cycle of thepower capping signal POW_CAP to update the normalization factor N. Inaddition, it is to be understood that the management interface 54 is notlimited to setting the duty-cycle of the power capping signal POW_CAP to100% and 0% in generating the normalization factor N, but could useother values, instead, to extrapolate the normalization factor N.

Also, although the example of FIG. 2 demonstrates that the predeterminedgain constant K is provided to the power controller 52, it is to beunderstood that the management interface 54 could be configured toprovide the predetermined gain constant K to the power controller 52, orcould be configured to provide the normalization factor N as a factorthat also includes the predetermined gain constant K, as described ingreater detail in the example of FIG. 3 below. As yet another example,it is to be understood that there are a variety of different ways thatthe power capping signal POW_CAP can be generated, such that the powercapping signal POW_CAP is not limited to being integrated and/orpulse-width modulated, as demonstrated in the example of FIG. 2, butcould be generated from a general Proportional/Integral/Derivative (PID)controller. For example, the control percentage of the power cappingsignal POW_CAP can be a range of analog magnitudes of the power cappingsignal POW_CAP instead of a duty-cycle. Furthermore, it is to beunderstood that there are a variety of ways that the error can benormalized in the example of FIG. 2. For example, the normalizationfactor can be arithmetically applied to data factors other than thepredetermined gain constant K and/or the error factor ERR, such as thepower feedback signal POW_FB or the power capping signal POW_CAP. Thus,the power capping system 50 can be configured in a variety of ways.

FIG. 3 illustrates an example embodiment of a data conversion system 100in a power capping system. As an example, the data conversion system 100Can be implemented in the power capping system 10 in the example of FIG.1 or the power capping system 50 in the example of FIG. 2. Therefore,reference is to be made to the examples of FIGS. 1 and 2 in thefollowing description of FIG. 3.

The data conversion system 100 includes a power controller 102 and amanagement interface 104. As an example, the power controller 102 andthe management interface 104 can correspond to the power controller 52and the management interface 54 in the example of FIG. 2. However, it isto be understood that, in the example of FIG. 3, the power controller102 and the management interface 104 are demonstrated simplistically. Assuch, only a portion of each device is demonstrated in the example ofFIG. 3. In the example of FIG. 3, the power controller 102 and themanagement interface 104 can be configured as dissimilar bit-processors,such as with respect to certain mathematical operations (e.g.,multiplication/division). As such, data conversion may be necessary withrespect to the arithmetic calculations, such as calculation of the errorfactor ERR and the normalization factor N, that are performed betweenthe two devices. For example, the power controller 102 can be configuredas an 8-bit processor that is unable to perform division, and themanagement interface 104 can be configured as a 32-bit processor.

The power controller 102 includes a data converter 106 that converts theerror factor ERR to a converted error factor ERR_CONV. As an example,the data converter 106 truncates the error factor ERR to a binaryfloating point number with a lesser number of bits. Specifically, theerror factor ERR can be generated as an unsigned integer (e.g., 18-bit)that could have a negative value. The data converter 106 can thusconvert the error factor ERR into a form ε×2^(i), where ε can be aninteger significand of lesser bits (e.g., 7-bit) and the 2^(i) term isindicative of the magnitude of the converted error factor ERR_CONV withrespect to the bit-range of the error factor ERR. Thus, truncating theerror factor ERR to 7-bits introduces only approximately 1/128 (0.8%) orless error in the subsequent calculations.

Similarly, the management interface 104 includes a data converter 108that converts the normalization factor N to a converted normalizationfactor N_CONV. As an example, the data converter 108 truncates thenormalization factor N to a binary floating point number with a lessernumber of bits. Specifically, the normalization factor N can begenerated as an unsigned integer (e.g., 14-bit). The data converter 108can thus convert the normalization factor N into a form n×2^(i), where ncan be an integer significand of lesser bits (e.g., 9-bit) and the 2^(i)term is indicative of the magnitude of the converted normalizationfactor N_CONV with respect to the bit-range of the normalization factorN.

The management interface 104 includes a gain multiplier calculator 110that is configured to multiply the converted normalization factor N_CONVwith the predetermined gain constant K. As an example, the powercontroller 106 may be configured as a processor with lesser processingcapabilities relative to the management interface 104. Thus, the powercontroller 102 may not be able to perform division. Thus, the divisionof the error and the predetermined gain factor K by the normalizationfactor N (i.e., the converted normalization factor N_CONV) may beperformed in the management interface 104, particularly by the gainmultiplier calculator 110. Thus, the gain multiplier calculator 110generates a gain factor M that includes the component of thepredetermined gain factor K. In particular, the gain multipliercalculator 110 can convert the predetermined gain factor K into a factork×2⁻⁴, and can calculate a factor m=(k×2¹¹)/n. Thus, the gain factor Mcan be equal to (K×2¹⁰)/N, or m×2^(−j−5). As such, the gain factor M canbe multi_(p)lied by the converted error factor ERR_CONV by a multiplier112 to generate the normalized error N_ERR in the power controller 102.Accordingly, the normalized error N_ERR can be equal to m×2^(−j−5).

It is to be understood that the data conversion system 100 is notintended to be limited to the example of FIG. 3. As an example,depending on the complexity of the server and/or one or both of thepower controller 102 and the management interface 104, the dataconverter 106 or the data converter 108 may be omitted. Specifically,the example of FIG. 3 demonstrates that a normalized error N_ERR can becalculated despite the power controller 102 and the management interface104 being configured as dissimilar bit-processors. Thus, one or both ofthe data converters 106 and 108 can be omitted depending on thesimilarity of processing capability of the server, the power controller102, and/or the management interface 104. Accordingly, the dataconversion system can be configured in a variety of ways.

FIG. 4 illustrates yet another example embodiment of a power cappingsystem 150. The power capping system 150 can be implemented tosubstantially limit a power consumption associated with a plurality ofservers 152, demonstrated in the example of FIG. 4 as SERVER 1 throughSERVER X, where X is an integer greater than one, that each include oneor more processors and/or memory devices (not shown). As an example, theservers 152 can each provide separate and distinct processingcapabilities and resources, and can thus each consume separate anddistinct ranges of power.

The power capping system 150 includes a respective plurality of powercapping sub-systems 154 that provide power capping capability to each ofthe plurality of servers 152. Each of the power capping sub-systems 154can be configured substantially similar to the power capping systems 10and 50 in the examples of FIGS. 1 and 2. Specifically, each of the powercapping sub-systems 154 includes a power controller 156 and a managementinterface 158. The power controller 156 can implement a control loop togenerate a power capping signal POW_CAP₁ through POW_CAP_(X) that isprovided to a respective one of the servers 152 to substantially limitthe power consumption of the server 152. The power capping signalsPOW_CAP₁ through POW_CAP_(X) can have a control percentage that is setbased on an error of power feedback associated with the respective oneof the servers 152 relative to a predetermined maximum desired power anda predetermined gain factor K. The management interface 158 isconfigured to generate a normalization factor N₁ through N_(X) that isprovided to the power controller 156 to normalize the error, similar toas described above in the examples of FIGS. 1 and 2, such as during acalibration procedure.

Because the management interface 158 of each of the power cappingsub-systems 154 generates the normalization factor N₁ through N_(X), thepredetermined gain factor K can be provided as a single value to all ofthe power capping sub-systems 154. Therefore, in the example of FIG. 3,the predetermined gain factor K is not calculated separately for each ofthe servers 152. In other words, the servers 152 are not individuallytuned, such as at a time of manufacture or fabrication, to determinespecific power capping needs, but can instead be calibrated individuallyto normalize the error factors N₁ through N_(X) for specific powercapping demands.

It is to be understood that the power capping system 150 is not intendedto be limited to the example of FIG. 4. As an example, one or more ofthe power capping sub-systems 154 can include data conversion features,such as similar to the data conversion system 100 in the example of FIG.3, based on processing dissimilarities associated with the servers 152,the power controllers 156 and/or the management interfaces 158. Asanother example, the predetermined gain factor K is not limited to asingle value for each of the power capping sub-systems 154, but couldinclude two or more values for providing an amount of gain for powercapping. Thus, the power capping system 150 can be configured in avariety of ways.

In view of the foregoing structural and functional features describedabove, a methodology in accordance with various embodiments of thepresent invention will be better appreciated with reference to FIG. 5.While, for purposes of simplicity of explanation, the methodology ofFIG. 5 is shown and described as executing serially, it is to beunderstood and appreciated that the present invention is not limited bythe illustrated order, as some embodiments could, in accordance with thepresent invention, occur in different orders and/or concurrently withother embodiments from that shown and described herein. Moreover, notall illustrated features may be required to implement a methodology inaccordance with an embodiment of the present invention.

FIG. 5 illustrates an example of a method 200 for normalizing error in apower capping system associated with a server. At 202, a calibrationprocedure is initiated. At 204, a control percentage associated with apower capping signal that is provided to the server to substantiallylimit the power consumption of the server is adjusted. At 206, anormalization factor is generated based on a difference between theactual power consumption of the server when the control percentage isset at a first value and when the control percentage is set at a secondvalue. At 208, an error between a predefined maximum desired power andthe actual power consumption of the server is normalized based on thenormalization factor. At 210, the control percentage of the powercapping signal is set based on the normalized error during normaloperation of the power capping system.

What have been described above are examples of the invention. It is, ofcourse, not possible to describe every conceivable combination ofcomponents or methodologies for purposes of describing the invention,but one of ordinary skill in the art will recognize that many furthercombinations and permutations of the invention are possible.Accordingly, the invention is intended to embrace all such alterations,modifications, and variations that fall within the scope of thisapplication, including the appended claims.

What is claimed is:
 1. A power capping system comprising: a powercontroller configured to calculate an error between a predefined maximumdesired power and a power feedback signal associated with actual powerconsumption of a server and to provide a power capping signal thatsubstantially limits the power consumption of the server based on apredetermined gain constant and the error; and a management interface toinstruct the server to run a processing intense program and to generatea normalization factor based on a magnitude of the power feedback signalset during the running of the processing intense program, thenormalization factor being implemented to normalize the error.
 2. Thesystem of claim 1, wherein the management interface is furtherconfigured to initiate a calibration procedure and to adjust a controlpercentage associated with the power capping signal during thecalibration procedure to calculate a difference in the power feedbacksignal between the control percentage set at a first value and set at asecond value, the normalization factor being generated based on thedifference.
 3. The system of claim 2, wherein the management interfaceis further configured, during the calibration process, to instruct theserver to run the processing intense program to set the magnitude of thepower feedback signal to a substantially maximum value independently ofthe control percentage of the power capping signal.
 4. The system ofclaim 1, wherein the power controller and the management interface areconfigured as dissimilar bit-processors, and wherein at least one of thepower controller and the management interface comprise a data converterconfigured to convert at least one of the error and the normalizationfactor, respectively, to a digital signal having a predetermined numberat bits.
 5. The system of claim 1, wherein the power capping system isone of a plurality of power capping systems, each of the plurality ofpower capping systems comprising a power controller and a managementinterface that manage a power associated with a respective plurality ofindividual servers the predetermined gain constant being provided toeach of the plurality of power capping systems.
 6. An integrated circuitcomprising at least one of the power controller and the managementinterface in the power capping system of claim
 1. 7. The system of claim1, wherein the processing intense program comprises a predeterminedseries of processing operations to substantially maximize powerconsumption of the server.
 8. A method for normalizing error in a powercapping system associated with a server, the method comprising:initiating a calibration procedure; adjusting a control percentageassociated with a power capping signal that is provided to the server tosubstantially limit the power consumption of the server generating anormalization factor based on a difference between the actual powerconsumption of the server when the control percentage is set at a firstvalue and when the control percentage is set at a second value;normalizing an error between a predefined maximum desired power and theactual power consumption of the server based on the normalizationfactor; and setting the control percentage of the power capping signalbased on the normalized error during normal operation of the powercapping system.
 9. The method of claim 8, wherein generating thenormalization factor comprises generating the normalization factor basedon a difference between the actual power consumption of the server whenthe control percentage is set at approximately 100% and when the controlpercentage is set at approximately 0%.
 10. The method of claim 8,further comprising instructing the server to run a processing intenseprogram to substantially maximize power consumption of the serverindependently of the power capping signal.
 11. The method of claim 8,further comprising: converting at least one at the error and thenormalization factor, respectively, to a digital signal having apredetermined number of bits; and dividing the error by thenormalization factor at the predetermined number of bits to normalizethe error.
 12. The method of claim 8, wherein generating a normalizationfactor comprises generating a plurality of normalization factorsassociated with each of a plurality of servers, the plurality ofnormalization factors each being configured to normalize errorassociated with a respective one of a plurality of power feedbacksignals relative to the predetermined gain constant that is common toeach of the plurality of servers.
 13. A power capping system comprising:a plurality of power controllers that are each configured to calculatean error between a predefined maximum desired power and a power feedbacksignal associated with one of a respective plurality of servers thateach comprise at least one processor, the plurality of power controllerseach being further configured to provide a power capping signal to therespective one of the plurality of servers based on the error and apredetermined gain constant associated with all of the plurality ofservers, the power capping signal being configured to substantiallylimit the power consumption of the respective one of the plurality ofservers; and a plurality of management interfaces that are eachconfigured to generate a normalization factor configured to normalizethe error associated with the respective one of the plurality of serversbased on the power feedback signal.
 14. The system of claim 13, whereinthe plurality of management interfaces are configured to generate thenormalization factor during one of a calibration procedure andperiodically during real-time operation of the respective plurality ofservers.
 15. The system of claim 13, wherein each of the plurality ofmanagement interfaces is further configured, during the calibrationprocedure, to adjust a control percentage associated with the respectivepower capping signal and to calculate a difference in the respectivepower feedback signal between the control percentage set at a firstvalue and set at a second value, the normalization factor beinggenerated based on the difference.
 16. The system of claim 13, whereineach of the plurality of management interfaces is further configured,during the calibration process, to instruct the respective one of theplurality of servers to run a processing intense program to set amagnitude of the respective power feedback signal to a substantiallymaximum value independently of the respective power capping signal.